SPEC-PWF-PON · v0.1
13 June 2026
Owner: Platform team

1Trigger, outcome & lanes

What starts this process, where it ends, who acts and on which surfaces. The journey mirrors the customer one with two deliberate differences — the partner front door is partner.riversync.com, and the partner program (Partners-app access + channel subtype) is gated behind a RiverSync approval that the basic account is not.

2The flow

Top to bottom in sequence; lanes are the actors. The basic account goes live the moment email is verified; in parallel RiverSync reviews the application and — on approval — assigns the channel subtype and unlocks the Partners app. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions.

3Steps

Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.

4Related documentation

Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.

5Rules in play

The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.

6Open questions & ⚠ gaps

Surfaced by this process; not yet resolved in the model. To be reconciled into the PRD/ERD cascade.

Ref	Gap
PAR-7 ⚠	Partner self-application & program approval. The application form (proof of legitimacy, registration, tax ID), the RiverSync review/approve gate, and the partner.approved event are new — proposed requirement PAR-7 does not yet exist; add it plus a PartnerApplication entity and the gated-program state in the ERD.
FED-8 ⚠	Partner Owner role. Partner tenants get an explicit fixed-full Owner (symmetric with customers) rather than defaulting to Administrator — proposed FED-8; reconcile with the Federation PRD role model.
AUTH-2	Membership-gating the Partners app. Basic account active at verification, Partners app unlocked only on approval — confirm the two-state grant in AUTH-2 and the AppRoleGrant model.
PRT-9	Subtype is RiverSync-set. Distributor/reseller assigned at approval, never selected by the applicant (existing rule, asserted here).

7Revision history

Version	Date	Changes
0.1	13 Jun 2026	First draft — new partner front door, split from the former combined onboarding workflow. Shares the customer spine; adds the partner-program approval gate, subtype assignment (PRT-9) and the explicit partner Owner role.